Skip to content

chore(next): release adcp-reporting-storage 0.2.0-beta.5 - #1884

Open
aao-ipr-bot[bot] wants to merge 2 commits into
nextfrom
release-please--branches--next--components--adcp-reporting-storage
Open

aao-ipr-bot[bot] wants to merge 2 commits into
nextfrom
release-please--branches--next--components--adcp-reporting-storage

Conversation

@aao-ipr-bot

@aao-ipr-bot aao-ipr-bot Bot commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.2.0-beta.5 (2026-11-10)

Features

  • reporting: notify the adopter when a reporting issue opens, escalates or resolves (#1875) (74bbe6f)

This PR was generated with Release Please. See documentation.

@aao-secretariat

Copy link
Copy Markdown

Ladon does not review bot-authored PRs.

@aao-ipr-bot
aao-ipr-bot Bot force-pushed the release-please--branches--next--components--adcp-reporting-storage branch from eccb557 to 4093693 Compare November 9, 2026 05:32
@aao-ipr-bot
aao-ipr-bot Bot force-pushed the release-please--branches--next--components--adcp-reporting-storage branch from ec13cf5 to fc2937e Compare November 10, 2026 12:22

@KonstantinMirin KonstantinMirin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd close this rather than merge it. Nothing under packages/adcp-reporting-storage has changed since adcp-reporting-storage-v0.2.0-beta.4, so 0.2.0b5 would be the same wheel as 0.2.0b4 under a new version. The one changelog line credits #1875 (74bbe6f), which touched only src/adcp, docs and tests, and the same line is already in adcp 10.0.0-beta.15. It ends up here because #1875 was stacked on #1874, so its GitHub file list still names the storage files #1874 had already merged, and release-please attributes by that list. Release-please will probably regenerate this PR on the next push to next, so the lasting fix is to let the next real storage change carry the release and drop this line from that PR.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant